Skip to content

Conversation

@henrymercer
Copy link
Contributor

Clean up this FF now it has been successfully rolled out.

Risk assessment

For internal use only. Please select the risk level of this change:

  • Low risk: Changes are fully under feature flags, or have been fully tested and validated in pre-production environments and are highly observable, or are documentation or test only.

Which use cases does this change impact?

  • Advanced setup - Impacts users who have custom workflows.
  • Default setup - Impacts users who use default setup.
  • Code Scanning - Impacts Code Scanning (i.e. analysis-kinds: code-scanning).
  • Code Quality - Impacts Code Quality (i.e. analysis-kinds: code-quality).
  • GHES - Impacts GitHub Enterprise Server.

How did/will you validate this change?

  • Unit tests - I am depending on unit test coverage (i.e. tests in .test.ts files).
  • End-to-end tests - I am depending on PR checks (i.e. tests in pr-checks).

If something goes wrong after this change is released, what are the mitigation and rollback strategies?

  • Rollback - Change can only be disabled by rolling back the release or releasing a new version with a fix.

How will you know if something goes wrong after this change is released?

  • Telemetry - I rely on existing telemetry or have made changes to the telemetry.
    • Alerts - New or existing monitors will trip if something goes wrong with this change.

Merge / deployment checklist

  • Confirm this change is backwards compatible with existing workflows.
  • Consider adding a changelog entry for this change.
  • Confirm the readme and docs have been updated if necessary.

@github-actions github-actions bot added the size/S Should be easy to review label Oct 22, 2025
@henrymercer henrymercer force-pushed the henrymercer/clean-up-resolve-languages-ff branch from 5afb9b9 to a691497 Compare October 22, 2025 16:04
@henrymercer henrymercer marked this pull request as ready for review October 30, 2025 13:49
@henrymercer henrymercer requested a review from a team as a code owner October 30, 2025 13:49
Copilot AI review requested due to automatic review settings October 30, 2025 13:49
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR removes the resolve_supported_languages_using_cli feature flag and its associated infrastructure, as it has been successfully rolled out and is no longer needed. The change simplifies the codebase by replacing feature flag checks with direct calls to codeql.supportsFeature() to determine if the CLI supports the BuiltinExtractorsSpecifyDefaultQueries tools feature.

Key Changes

  • Removed the ResolveSupportedLanguagesUsingCli feature flag enum value and configuration
  • Updated getSupportedLanguageMap() to check for CLI support directly instead of using the feature flag
  • Removed the features parameter from getLanguages() and initActionState() functions
  • Simplified test cases by removing the feature flag variations

Reviewed Changes

Copilot reviewed 15 out of 15 changed files in this pull request and generated no comments.

File Description
src/feature-flags.ts Removed ResolveSupportedLanguagesUsingCli feature flag definition and configuration
src/config-utils.ts Replaced feature flag check with direct CLI feature support check and removed features parameter
src/config-utils.test.ts Removed test iterations for feature flag variations, keeping only the enabled behavior
lib/*.js Generated JavaScript code reflecting the TypeScript changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/S Should be easy to review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants